chore(deps): update local-path-provisioner docker tag to v0.0.37 - #166
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update local-path-provisioner docker tag to v0.0.37#166renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Helm Template Diff —
|
Owner
Renovate Review:
|
| Check | Result |
|---|---|
| Inputs | Complete — full ### Release Notes section (rancher/local-path-provisioner v0.0.37) and a matching rendered-diff comment (03-apps-apps-local-path-provisioner, 77 changed lines, no truncation) |
| Description vs. diff | Consistent — table says 0.0.36 → 0.0.37; the only changed file, 03_apps/apps/local-path-provisioner/app.yaml, bumps helm.version from 0.0.36 to 0.0.37, nothing else touched |
| Rendered diff | Full, no truncation — not label-only: beyond the helm.sh/chart/app.kubernetes.io/version label churn and the Pulled/Digest/image-tag lines, the Deployment container spec gains a HEALTH_PORT=8080 env var, a new containerPort: 8080 (health), and new startupProbe/livenessProbe/readinessProbe blocks hitting /health and /ready |
| Changelog vs. config | No breaking changes, renamed/removed keys, or CRD changes in the changelog. The new probes correspond to changelog item "Add initial /health probe" (upstream rancher/local-path-provisioner#583), which ships in this same v0.0.37 release, so the image and the probes are correctly paired. 03_apps/apps/local-path-provisioner/values.yaml sets no probe overrides, so the chart's new defaults apply uncontested |
Details:
- The existing
ClusterRole,ClusterRoleBinding, and two namespacedRole/RoleBindingpairs in the diff show only label-line changes — theirrules:/roleRef:blocks are byte-identical old vs. new, so this is not an RBAC finding (per the "label-bump only" exclusion). startupProbeusesfailureThreshold: 12atperiodSeconds: 5(60s grace) beforelivenessProbetakes over — a conservative default, low risk of falsely killing a still-starting pod.- The changelog also lists "add storageclass nodeaffinity to helm values" (upstream #581) as a new opt-in value;
values.yaml's twostorageClassConfigsentries (local-path,local-path-auto-delete) don't set it, so this component doesn't inherit any behavior change from it — see Worth noting.
Worth noting (non-blocking):
- The new "storageclass nodeaffinity" helm value (upstream #581) isn't set anywhere in
values.yaml— worth evaluating for node-pinning given the fixed/opt/local-path-provisionerhost path used by both storage classes here. - This release also bundles two upstream CVE fixes (
golang.org/x/net,golang.org/x/text) in the provisioner's Go module deps — a supply-chain-hygiene reason to take the bump even though functionally unrelated to this repo's usage.
Why MEDIUM: Patch bump with a clean changelog (no breaking/renamed/CRD items), but the rendered diff is not label-only — it adds new container health-probe behavior to the Deployment, a genuine (well-paired, plausibly harmless, but real) behavior change.
Generated by Claude Code
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.0.36→0.0.37Release Notes
rancher/local-path-provisioner (local-path-provisioner)
v0.0.37: Local Path Provisioner v0.0.37Compare Source
What's Changed
4187e74by @renovate-rancher[bot] in #592d1ba80aby @renovate-rancher[bot] in #603New Contributors
Full Changelog: rancher/local-path-provisioner@v0.0.36...v0.0.37
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.